-
Notifications
You must be signed in to change notification settings - Fork 583
Htop sorting CPU% column incorrectly #810
Comments
I remember seeing this for like the past year or more. Reproducing on ubuntu right now. If you, say, sort by memory, then sort by cpu and then do nothing, I think the sorting is correct. As soon as I move the highlighted line up or down, sorting breaks. |
I am also seeing this, for some time (over a year). After interacting with the list like moving the highlighted row, it goes out of order. The ordering is trending in the right order (it isn't a random ordering) but many entries are not in the correct sorted position. Re-triggering the sort by CPU fixes the ordering. Looking at it again now, it seems that over time after sufficiently many updates and re-writes of the terminal during which time there were no input/interactions with it, the ordering stabilizes back in sorted order. My version is htop 2.2.0 on Arch Linux, but I have also observed it on Centos 7 and Ubuntu 18.04. |
Same issue with htop 2.2.0 running on Termux (Android app supplying a real Linux userspace) using tsu (su to root, while keeping Termux userspace). Deleting |
I see this on my Mac, 10.14.6. Keep it running long enough, particularly under high CPU load and htop forgets this default order. Quit and restart it, and it's working again. |
Sometimes when I'm trying to diagnose what process is hogging all of my laptops resources, I notice that htop will sort the CPU% column incorrectly. Example below:
The CPU% column is highlighted in the header row, so that means its sorting by that column (right?), yet its all out of order. Its clearly not sorting it numerically, and neither is it sorting it lexicographically. I'm not sure how else it could be trying to sort it.
Some Details:
Here's the content of my
~/.config/htop/htoprc
file.I wasn't able to find much on it after consulting with the Google Gods. Is this a known bug? Or is it perhaps a PEBKAC error? (i hope not, that would be embarrassing)
Any input is appreciated.
Thanks!
-J
The text was updated successfully, but these errors were encountered: